se.cs.ieu.edu.tr
Course Name | |
Code | Semester | Theory (hour/week) | Application/Lab (hour/week) | Local Credits | ECTS |
---|---|---|---|---|---|
Spring |
Prerequisites | None | |||||
Course Language | ||||||
Course Type | Required | |||||
Course Level | - | |||||
Mode of Delivery | - | |||||
Teaching Methods and Techniques of the Course | ||||||
Course Coordinator | ||||||
Course Lecturer(s) | ||||||
Assistant(s) | - |
Course Objectives | |
Learning Outcomes | The students who succeeded in this course;
|
Course Description |
| Core Courses | X |
Major Area Courses | ||
Supportive Courses | ||
Media and Managment Skills Courses | ||
Transferable Skill Courses |
Week | Subjects | Required Materials |
1 | Introduction to human computer interaction | Designing the User Interface, Ben Shneiderman, (ch 1). |
2 | Usability of ınteractive systems | Designing the User Interface, Ben Shneiderman, (ch 1). |
3 | Guidelines, principles, and theories | Designing the User Interface, Ben Shneiderman, (ch 2). |
4 | Managing design processes | Designing the User Interface, Ben Shneiderman, (ch 3). |
5 | Managing design processes | Designing the User Interface, Ben Shneiderman, (ch 3). |
6 | Evaluating interface designs | Designing the User Interface, Ben Shneiderman, (ch 4). |
7 | Evaluating interface designs | Designing the User Interface, Ben Shneiderman, (ch 4). |
8 | Evaluating interface designs | Designing the User Interface, Ben Shneiderman, (ch 4). |
9 | Midterm | |
10 | Direct manipulation and virtual environments | Designing the User Interface, Ben Shneiderman, (ch 5). |
11 | Menu selection, form fillin, and dialog boxes | Designing the User Interface, Ben Shneiderman, (ch 6). |
12 | Interaction devices | Designing the User Interface, Ben Shneiderman, (ch 8). |
13 | Collaboration and social media participation | Designing the User Interface, Ben Shneiderman, (ch 9). |
14 | Command and natural languages | Designing the User Interface, Ben Shneiderman, (ch 7). |
15 | Project review | |
16 | Review of the semester |
Course Notes/Textbooks | Ben Shneiderman, Catherine Plaisant, Maxine Cohen, Steven Jacobs, 2009, Designing the User Interface: Strategies for Effective HumanComputer Interaction (5th Edition), Addison Wesley |
Suggested Readings/Materials | Selected papers that are posted on the web page. |
Semester Activities | Number | Weigthing |
Participation | ||
Laboratory / Application | ||
Field Work | ||
Quizzes / Studio Critiques | ||
Portfolio | ||
Homework / Assignments | 6 | 30 |
Presentation / Jury | ||
Project | ||
Seminar / Workshop | ||
Oral Exam | ||
Midterm | 1 | 30 |
Final Exam | 1 | 40 |
Total |
Weighting of Semester Activities on the Final Grade | 7 | 60 |
Weighting of End-of-Semester Activities on the Final Grade | 1 | 40 |
Total |
Semester Activities | Number | Duration (Hours) | Workload |
---|---|---|---|
Course Hours (Including exam week: 16 x total hours) | 16 | 3 | 48 |
Laboratory / Application Hours (Including exam week: 16 x total hours) | 16 | ||
Study Hours Out of Class | 16 | 1 | |
Field Work | |||
Quizzes / Studio Critiques | |||
Portfolio | |||
Homework / Assignments | 6 | 3 | |
Presentation / Jury | |||
Project | |||
Seminar / Workshop | |||
Oral Exam | |||
Midterms | 1 | 18 | |
Final Exams | 1 | 20 | |
Total | 120 |
# | Program Competencies/Outcomes | * Contribution Level | ||||
1 | 2 | 3 | 4 | 5 | ||
1 | Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute | X | ||||
2 | Be able to design and analyze software at component, subsystem, and software architecture level | X | ||||
3 | Be able to develop software by coding, verifying, doing unit testing and debugging | X | ||||
4 | Be able to verify software by testing its behaviour, execution conditions, and expected results | X | ||||
5 | Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation | X | ||||
6 | Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically | X | ||||
7 | To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning | X | ||||
8 | Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes | X | ||||
9 | Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance | X | ||||
10 | To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software | X | ||||
11 | To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering | X | ||||
12 | Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering | X | ||||
13 | Be able to use a foreign language to follow related field publications and communicate with colleagues | X |
*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest